Method of non-intrusive analysis of secure and non-secure web application traffic in real-time

ABSTRACT

Provided is a method and system for monitoring and analysis of networked systems, that is non-intrusive and real time. Both secure and non-secure traffic may be analyzed. The provided method involves non-intrusively copying data from a communication medium, reconstructing this data to a higher level of communication, such as the application level, grouping the data into sets, each set representing a session, and organizing the data for chosen sessions in hierarchical fashion which corresponds to the hierarchy of the communicated information. If monitored communications are encrypted, they are non-intrusively decrypted in real time. Hierarchically reconstructed session data is used by one or more plug-in applications, such as alarms, archival applications, visualization applications, script generation applications, abandonment monitoring applications, error detection applications, performance monitoring applications, and others.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 10/455,798 (Attorney Docket No. BOR-007), filed May 30, 2003and entitled “Method of Non-Intrusive Analysis of Secure and Non-SecureWeb Application Traffic in Real-Time,” all of which is hereinincorporated by reference for all purposes.

FIELD

This invention relates generally to computing systems and morespecifically to the testing, auditing and monitoring of networkedcomputing systems.

BACKGROUND

The wide adoption of the Internet, and networked computing in generalhas resulted in the proliferation of networked computing systems.Networked computing systems may consist of various computers or otherdevices that communicate over a network. For computer networking aclient server terminology is often used. A computer that makes a requestover a network is referred to as a client and a computer that receivessuch a request and replies to it is referred to as a server. Sincenetworked computing systems may be very complex and may be used formission critical tasks, testing of these systems is very important.Furthermore, these systems may need to be monitored. Monitoring can havemany uses such as auditing, identifying errors, or monitoring thebehavior of clients who are using a server.

The testing, auditing and monitoring tasks may be accomplished byutilizing features of the software that runs on the computers of thesesystems. Most networking software, especially server software, includescertain testing, monitoring and auditing capabilities. But, utilizingthese features may change the environment being tested or monitored. Forexample, if a server's speed of replying to certain requests is beingmonitored utilizing a monitoring feature of the server, the monitoringfeature itself will use processor time and thus affect the speed withwhich the processor replies to requests. If software is being monitoredto discover errors, the monitoring feature of the software adds an extralevel of complexity which can itself be the cause of errors. Thetendency of a monitoring feature to change the environment beingmonitored is called intrusiveness. Intrusive monitoring features usuallypose an increasing risk of destabilizing the system or skewing theresults of monitoring operations.

Encryption is often used in network communications. Monitoring encryptedinformation can be difficult, especially if such monitoring is to beperformed in a non-intrusive fashion. For monitoring to be effective theinformation must be decrypted.

In order for monitoring to be effective for some purposes, it needs tobe performed in real time, i.e., within a relatively short time of thecommunications being monitored. For example, for some serverinstallations it is advantageous for errors to be detected and handledshortly after they occur. Thus, it would be advantageous to have analert or alarm that goes off as soon as an error occurs. Similarly,alarms are useful for other kinds of events, such as degradations ofperformance. Furthermore, it may be advantageous for a server operator,or a support professional to know at any given time the way clients arecurrently using the server. If the systems that are being monitored aresensitive to downtime, it is desired that diagnostic information isobtained very soon after any errors (or other performance relatedevents) are detected, so they can be addressed with minimal degradationto performance. Real time monitoring also allows for early discarding ofunnecessary data. Some non-real time monitoring applications createlarge dump files of raw monitoring data that contain mostly unnecessarydata and take up valuable system resources.

The communications between a server and a client may be quite complex.In particular any single communication may refer to or depend oninformation from other communications. Thus, it is important formonitoring purposes that related communications are examined togetherand their relationships noted. For example, in the case ofcommunications in HTTP, an HTML page may refer to various picture filesor frame files that have been sent at a previous time, or which must besent at a later time.

Modern computer networking is usually described by the OSI seven layermodel which is well known in the art. According to the model, data sentover a network may change its form as it passes through the utilitiesthat service each layer. For example, at the network layer data is splitup into packets and header information is added to each packet. As it ispassed through a network cable the data is considered to be in layer 1form. However, for many monitoring and testing purposes, other layersare more relevant. For example, when monitoring is done from theend-user's perspective, layer 7 is most relevant, layer 7 information isclosest in form to the information entered or viewed by the end-user.

There are several known types of monitoring applications. One of them isthe proxy. Proxies are usually placed on a communication channel betweentwo or more monitored machines and actively forward messages betweenthese machines. Proxies are intrusive, because in order to use proxiesthe monitored machines must be configured to address theircommunications to the proxy. Another intrusive feature of proxies isthat they add a point of failure, that is a failure of the proxy willaffect the communications going through it. In fact a failure of theproxy usually means no communications can go through it. Proxies alsocause delays in communications.

Another known type of monitoring application is a server side plug-in.The server side plug-in is a software function that interacts with aserver by way of an interface of the server, created specifically forserver side plug-ins. Examples of such interfaces for web servers areISAPI, NSAPI and CGI. Occasionally, the server side plug-in is directlyinserted in the server software and executed by the server whenpredefined conditions occur. Different servers have different plug-ininterfaces, thus a server plug-in will have to be specificallyconfigured for use with one or more types of servers. Server plug-insusually have access to OSI level 7 data (which may include thedecryption of encrypted communications). But, server plug-ins change thebehavior of the server by actively interacting with it. Thus, they areintrusive. The intrusive nature of server plug-ins causes performancedegradation and adds a point of failure (a failed server plug-in maycause failure or performance problems with the server).

Another known type of monitoring application is the use of log files.Some communications applications, such as web servers, may be configuredto continuously add data about their operation to log files. For webservers, such data is usually the URL's of web pages that have beenserved. Log files require storage space and applications use upadditional processing resources when they add information to log files.Because the size of log files is limited by practical considerations,only limited amount of information is stored in log files. For example,message bodies are usually not stored in log files. Log files are alsointrusive, because an application needs to be configured to use a logfile. Thus, log files can degrade application performance, or even causefailures.

Network sniffers are non-intrusive type of monitoring devices. But, theydo not have access to encrypted information. They do not possess theability to reconstruct data to the application layer (OSI layer 7).Network sniffers usually do not process data in real time, but storedata for later processing. Some network sniffers, such as intrusiondetectors, may process data in real time in order to detect certainevents.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features of the present invention will be morereadily apparent from the following detailed description and drawings ofthe illustrative embodiments of the invention wherein like referencenumbers refer to similar elements and in which:

FIG. 1 is a block diagram of a network including a cable-tap;

FIG. 2 is a block diagram of the Real Time Session Reconstruction Unit;

FIG. 3 is a diagram of a connection stream;

FIG. 4 is a diagram of a transaction object;

FIG. 5 is a detailed diagram of the Real Time Session ReconstructionUnit;

FIG. 6 is a block diagram of a web application session;

FIG. 7 is a block diagram of a data structure representing a webpage;

FIG. 8 is a diagram of a hierarchically reconstructed session;

FIG. 9 is a diagram of the dataflow of the present invention; and

FIG. 10 is a diagram of an exemplary visualization and a generatedscript.

DETAILED DESCRIPTION

Referring now to FIG. 1, therein is shown a communication network with acable-tap 100. A cable-tap is a device that can non-intrusively copy allnetwork traffic passing (in both directions) through a cable. Aftercopying this traffic the cable-tap 100 sends it to a standard networkmodule 114. The standard network module 114 processes the traffic andsends it to the Real Time Web Application Session Reconstruction Unit(RTSRU) 112. In a preferred embodiment the RTSRU 112 and the standardnetwork module 114 are implemented on the same computer 116.

It is preferred that the cable-tap be fault tolerant, i.e., malfunctionswith the cable-tap do not affect the network traffic passing through thecable. The cable-tap 100 can be placed on a network cable that isexpected to carry communications of interest. For this reason, thecable-tap 100 should be placed in such a way that it can intercept alltraffic going between the computers which should be monitored. FIG. 1shows an example of such placement, where the cable-tap 100 is placed ona network cable 110 between the server 102 and the network device 104closest to the server. In this example the computers which should bemonitored are the server 102 and the clients 108. All network trafficpassing between the server 102, and clients 108 must go through thecable-tap 102. Another desirable feature of this placement is that onlytraffic of interest passes through the cable-tap 102. Other placementsallow for the monitoring of multiple servers and/or multiple-webapplications at the same time.

In place of cable tap 100, the present invention may also utilizedifferent methods to capture network traffic, such as utilizing amonitor port of a network switch, designed for this purpose (the RMONport). Alternatively, if the network configuration is such that alltraffic of interest passes through a hub, the network traffic may becaptured by simply attaching the standard network module 114 to the hub.

The network device 104 may be, but is not limited to, a router or aswitch. The network device 104 is not required nor is it a part of thepresent invention. It is merely shown as a reference point, such devicesbeing ubiquitous in most modern networks.

The clients 108 communicate with the server(s) 102 through the networkdevice 104 and the internet 106. The cable-tap 100 is non intrusive,which means it is invisible to the server 102, the network device 104and the clients 108. Thus, the elements behind the cable tap 100—thestandard network module 114, and the RTSRU 112 are non-intrusive aswell.

The standard network module 114 realizes the first three layers of theOSI model. It takes in network traffic in the physical layer (usuallyconsisting of Ethernet frames) from the cable-tap 100 and processes itto transport layer packets (such as, for example, TCP, UDP or WAPpackets). Possible implementations of the standard network module 114are well known in the art. For example, one such implementation mayinclude hardware elements, such as a network interface card (NIC),network drivers and programming interfaces that are part of mostoperating systems, a packet capture driver, and a packet filter. Thenetworking hardware of an ordinary personal computer system, in additionto a modern operating system (such as Linux, Unix, Windows, etc.) and agenerally available packet capture driver (which includes a packetfilter) are sufficient to serve the functions of the standard networkmodule 114. A suitable packet capture driver is WinPCAP, provided by theNetgroup of Politecnico di Torino, and available athttp://winpcap.polito.it.

The packet filter, within the packet capture driver is used to discardunnecessary packets, so as to not slow down the other components.Unnecessary packets are packets that are not sent to or from computersthat are being monitored, or are not part of the protocol or protocolsthe present invention is configured to monitor. The packet filter isconfigured with the IP addresses of all computers that are beingmonitored, and discards the packets that do not have these IP addresseslisted as either source or destination. Alternatively, the packet filtermay be configured with the IP addresses of computers that are to beignored and thus discard packets coming from or going to thesecomputers.

A NIC usually ignores any packets that are not addressed to the computerto which the NIC is attached. Yet, for the purposes of this invention,the RTSRU 112 must receive network traffic that is not addressed to it(or the computer it is implemented on), so the NIC(s) used must beconfigured to accept all packets. Most NICs feature such an option,which is usually referred to as promiscuous mode.

The clients 108 are computers, or other electronic devices. Thesecomputers may be operated by human end-users, also referred to ascustomers. The end-users or customers are persons that are usingcomputers online, and need not be aware of the present invention. Theyshould be distinguished from the user 209, who is a professional thatmay operate the present invention.

FIG. 2 is a block diagram of the Real Time Session Reconstruction UnitRTSRU 112. The RTSRU 112 receives as input the processed network layertraffic from the standard network module 114. At this point the networktraffic is in the form of transport layer packets (usually TCP or UDPpackets). These packets contain header and payload data. Header datarefers to data needed for the transportation and handling of packets,such as destination IP address, connection-ID, etc. Payload data is thedata that is meant to be communicated by the packets. The header of eachpacket identifies the connection to which this packet belongs to. Thestream creation unit 211 examines these packets, strips them of theirheader data and groups the remaining payloads into connection streams,each connection stream including the payloads of packets belonging to adifferent connection. The stream creation unit 211 also examines timinginformation in the headers of packets and using such informationarranges the payloads in chronological order in the stream.

The contents of a connection stream are shown in FIG. 3. The payloads ofthe packets appear in the connection stream 300 in the order in whichthey were received and reordered by the stream creation unit 211. Therelevant header data of the packets belonging to a connection is placedonce by the stream creation unit 211 in the beginning of the connectionstream corresponding to that connection. This data is referred to as theconnection meta information 303, and may include the client IPaddress/port, and the server IP address/port for the connection. Thestream creation unit 211 may optionally add monitoring information tothe connection meta information 303, such as, for example, time stampsindicating when the connection was initiated and when it ended, aconnect latency value indicating the time it took to establish theconnection, flags indicating if a connection was aborted/abandonedprematurely, or TCP packet latency information for estimating clientmodem speeds and/or calculating the time a server needs to prepare adocument (server busy time). Since a single connection includescommunications between two machines flowing in two directions, theconnection stream includes two sub-streams containing the payloads ofthe connection being transmitted in each direction. These are theinbound payload data stream 301 and the outbound payload data stream302. The terms “inbound” and “outbound” do not reference the RTSRU 112,because the RTSRU 112 receives only a copy of both streams and as suchdoes not actively take part in the client/server communication. In theembodiments described herein the inbound payload data stream refers tothe stream of data sent from the client to the server and the outboundpayload data stream refers to the stream of data sent from the server tothe client. When the connection which the connection stream representsis closed, the connection stream terminates.

Referring to FIG. 2, the message decoder 203 processes all activeconnection streams in parallel. The message decoder 203 processesconnection streams, by first decrypting the stream, if necessary, andbreaking up the data of the stream into information units, eachinformation unit comprising one or more related communications from thestream. In the embodiment shown in FIG. 2, the information units aretransactions, wherein each transaction generally represents a pair ofcommunications—a request and a response (although, as shown below, incertain circumstances a transaction may be missing a responsecommunication). The nature of the transaction and the decryption processare also described below. Once a transaction is formed by the messagedecoder 203, it is stored in the transaction storage 204 and it isoptionally sent to the transaction analyzer plug in 208. The transactionstorage 204 serves as a means to quickly store and retrievetransactions. It uses caching and compression techniques and is usuallyimplemented in a computer's main memory. The transaction analyzer plugin 208 scans recently created transactions in real time for predefinedevents of interest. Events of interest are events that may need to bemonitored in real time. Examples of such events are error messages,requests coming from certain clients, response times that exceedperformance thresholds, or specific predefined customer input.

The session reconstruction module 205 receives a command either from thetransaction analyzer plug in 208 or a user 209 to reconstruct thesession to which a transaction belongs. The transaction analyzer plug in208 or the user 209 indicate to the session reconstruction module 205the transaction for which a session is to be reconstructed. The sessionrefers to a set of all other transactions that are relevant. Sessionsand methods of identifying transactions as belonging to a session aredescribed below.

The session reconstruction module 205 communicates with the transactionstorage 204 in order to search for and retrieve transactions from thesame session. Once all the available transactions from a session areretrieved, the session reconstruction module 205 determines thedependencies between them and organizes them in a hierarchical manner.Dependencies between transactions are found by looking for references toa transaction in another transaction. Specific methods of doing that aredescribed below. The output of the RTSRU 112 is a hierarchicallyreconstructed session 230. This hierarchically reconstructed session maybe viewed by users for error analysis or other monitoring purposes. Itmay be archived for auditing purposes, or it may be used to create ascript, which may later be used to recreate the client servercommunication which gave rise to an event of interest. An example of anevent of interest is a transaction with an error message in its body.

The message decoder 203 receives as input a connection stream andoutputs a plurality of transactions. An exemplary transaction 400 isshown in FIG. 4, and includes a meta information field 401 whichcontains meta-information describing the transaction and the environmentin which it occurred. Meta information may include a transaction-ID, theprotocol in which the transaction was executed (for example, HTTP, RMI,FTP or WSP/WTP or SMPT), an identification number of the connection fromwhich the transaction was extracted (the connection number), as well asthe client and server IP address/port through which the transactioncommunications were sent and received. Since the transaction isextracted from a single connection stream, which implies a single TCPconnection, both the request and response communications will be sentbetween the same client and server IP addresses and ports. Themeta-information field may also include elements such as, for example,SSL session ID (if the communications that made up the transaction wereencrypted using the SSL protocol), and time stamps that may be used formonitoring purposes. The Transaction 400 also includes a request header402 and an optional request body 404, which together define the request,as well as a response header 403 and an optional response body 405,which together define the response.

FIG. 5 shows a more detailed view of the RTSRU 112 configured to processHTTP communications. The Stream Creation Unit 211 groups incomingtransport layer packets into connection streams 300.

The message decoder 203 includes three modules—the secure trafficdecryption unit 501, the Transport protocol decoder 502 and thetransaction assembler 503.

The secure traffic decryption unit 501 decrypts the connection stream300 if necessary. Encryption in web communications is usuallyaccomplished using the Secure Socket Layer (SSL) or a very similarprotocol called the Transport Layer Security protocol (TLS). The presentinvention may also be used in conjunction with other security protocols,such as, for example, the Wireless Transport Layer Security protocol(WTLS). The Secure Socket Layer may use several different encryptionalgorithms, or cipher suits, depending on the circumstances. However,SSL usually uses a combination of a public key encryption algorithm(such as RSA) and a conventional encryption algorithm (such as RC4, ortriple DES). The client generates a pre-master secret and using thepublic key encryption algorithm encrypts the pre-master secret and sendsit to the server. A session key is generated independently by the clientand the server using the pre-master secret. Since they use the samemethod of generating sessions keys and they base their session keys onthe same pre-master secret, the client and the server generate identicalsession keys. Session keys are later used to encrypt and decryptcommunications, by way of a conventional encryption algorithm. Thepublic key encryption algorithm uses private keys and public keys (whichare different from the session key), of which only the private keys canbe used for decryption.

The secure traffic decryption unit 501 decrypts a connection stream 300by decrypting both the inbound payload data stream 301 and the outboundpayload data stream 302. In this way it differs from mostencryption/decryption tools, because most such tools need to decrypt anincoming stream and encrypt an outgoing stream. In contrast to othermonitoring tools the present invention does not take active part insecure communications, i.e., it does not send messages to either theserver or the client nor does it participate in any key creation withthe server or the client. In order to accomplish decryption in a timelymanner the secure traffic decryption unit 501 needs the private key ofthe server (or the computer that will receive the pre-master secret).Usually providing the server's private key to another device would beconsidered a security flaw, since private keys are not meant to becommunicated to any other party (even the encrypting party). But sinceit may be assumed that usually the server's owner or operator will usethe present invention to monitor his/her own server, providing theserver's private key to the secure traffic decryption unit 501 does notpose significant security risks.

The secure traffic decryption unit 501 then uses the server's privatekey to decrypt the initial stage of the SSL communication. This initialstage is called the handshake, and it is the stage in which the serverand the client exchange the pre-master secret using public keyencryption. Having decrypted this first stage, the secure trafficdecryption unit 501 is in possession of a decrypted pre-master secret.There are different well-known methods of deriving a session key from apre-master secret, depending on which cipher is used. The secure trafficdecryption unit 501 chooses a suitable method, depending on the cipherused and generates the session key from the pre-master secret. Thesecure traffic decryption unit 501 then uses the session key to decryptthe rest of the SSL communication, which is conventionally encrypted,and provides it to the transport protocol decoder 502.

The transport protocol decoder 502 receives decrypted streams from thesecure traffic decryption unit 501 that are in layer 6 (the presentationlayer) of the OSI model. It processes these streams and outputs OSIlayer 7 (application layer) messages, such as HTTP requests andresponses. The transport protocol decoder 502 parses the inbound payloaddata stream 301 and the outbound payload data stream 302 to obtainrequest and response messages, respectively. Parsing is performed usingstandard HTTP parsing methods. Once obtained, these messages are savedin message objects that include a message header and an optional messagebody. These message objects, as well as the connection meta information303 from the connection stream 300, are sent to the transactionassembler 503.

The transaction assembler 503 receives the request and response messageobjects and attempts to find the corresponding response message for eachrequest message and vice versa. A request message and a response messageare corresponding if the response message contains the response of aparticular request, contained in the request message. Request andresponse message objects are matched by first arranging the requestmessage objects and the response message objects of a single connectionin chronological order, according to the time they were received by thetransaction assembler 503. Then the request and response message objectsare paired up according to their places in the respective chronologicalorders, the first request message object being paired with the firstresponse message object, the second request message object with thesecond response message object, and so on. This method is effectivebecause all messages belong to a single connection. In protocols likeHTTP, the server is expected to respond to requests from any particularconnection strictly in the order they were received.

Once it discovers a pair of corresponding request and response messageobjects, the transaction assembler 503 creates a transaction object 400from those two message objects, repeatedly. The transaction assembler503 sets fields 402, 404, 403 and 405 according to the information inthe pair of corresponding request and response message objects. Thetransaction assembler creates an unique transaction ID and saves it inthe transaction meta information field 401. The transaction assemblersets the other values in the meta information field 401 according to theconnection meta information 303 of the connection stream 300, andoptionally any other information that may be relevant, such as timestamps of messages signifying the time they were received by thetransaction assembler 503. Once the transaction assembler hassuccessfully created a transaction object, it passes that transactionobject to the transaction storage 204 and optionally to the transactionanalyzer plug in 208.

The transaction storage 204 includes a storage and cache management unit505 and a random access transaction memory 511. The storage and cachemanagement unit 505 stores the incoming transaction objects in a randomaccess transaction memory 511. The storage and cache management unit 505reduces redundancy by caching transactions or by using compressiontechniques. The random access transaction memory 511 provides areal-time interface for querying and retrieving sets of transactionobjects using parameters contained in the transaction meta-information401. The random access transaction memory 511 may be implemented using,for example, a FIFO ring buffer with a cache management tree. In theHTTP protocol, requests contain a universal resource locator (URL).Thus, the transactions that result from these requests also contain aURL. Since the URL is important in determining correlation betweenvarious transactions, in exemplary embodiments configured to handle theHTTP protocol, such as the one shown in FIG. 5, the random accesstransaction memory 511 has the ability to retrieve transactions by URLas well.

The optional transaction analyzer plug-in 208 analyzes transactionobjects in real time as soon as they are received from the transactionassembler 503. Incoming transactions are checked for the occurrences ofspecial conditions, such as those that are relevant to monitoring ortesting of the system, and may include, but are not limited to, errormessages in the transaction bodies, HTTP errors, transactions in whichtoo much time has elapsed between the request and the response, ortransactions which include specific input from an end-user. Once thetransaction analyzer plug in 208 determines a certain transaction is atransaction of interest, it sends that transaction to the sessionreconstruction module 205. When a special condition is detected thenature of the condition is saved and is associated with the transaction,so it can later be used in conjunction with the hierarchicallyreconstructed web application session 230 for various monitoringpurposes. Additionally, a user 209 can watch transactions as they passthrough the transaction analyzer plug-in 208 and select transactions ofinterest.

The function of the session reconstructions module 205 is to reconstructthe session to which a particular transaction of interest belongs. Inexemplary embodiments configured to process the HTTP protocol, thesession refers to a web application session.

A session in general is a way to group transactions so that the groupingis useful for monitoring purposes. Thus, a session is meant to show alarge picture, or a coherent process or action, accomplished by severaltransactions (it is, however, possible that a session consist of asingle transaction). In the specific case of web applications, a sessionis usually defined to start when an end-user enters a monitored website(a monitored website is a website hosted on a monitored server), and toend when the end-user leaves that website, or does nothing for aspecified period of time (this is referred to as a session timeout). Anexample of a web application session is shown in FIG. 6. The end-userreaches the first webpage 600 by entering a start URL in his/herbrowser. Furthermore, the end-user proceeds to other webpages 601-604from the same website by other actions, such as clicking on a hyperlink,submitting a form, or clicking the back button of the browser or by anautomated action performed by his or her computer, such as client sidecode execution. When the end-user closes his/her browser, the websession is terminated. In this example, the web session consists of alltransactions necessary to bring webpages 600-604 to the end-user and tosend the various commands to the web server.

Relevant transactions, or transactions belonging to the same session canbe identified because they have the same client IP address, the sameserver IP address, and the same SSL/TLS session ID. But sometimes(especially when there is no SSL/TLS session ID available) the abovefactors may result in grouping transactions from more than one websession together. Thus, additional factors may be necessary.Fortunately, since complex websites often need to recognize sessions aswell, many such websites use some additional form of session ID.Virtually any website that requires log-in or uses a “shopping cart”,has a way of including a session ID with communications with the client.This session ID may be found in HTTP cookie headers, or as part of therequested URL path or within the HTTP-response body as a hidden formfield in an HTML document. This session ID is also used as an importantcomponent in identifying relevant transactions.

Referring to FIG. 5, a transaction of interest may be selected either byusing the transaction analyzer plug in 208, which identifies a selectedtransaction to the session reconstruction module 205, or by a user 209who may identify a transaction to the session reconstruction module 205by means of a suitable user interface.

A transaction sent from the transaction analyzer plug-in 208 or the user209 first reaches the meta information based transaction pre-selectionunit 520 (the meta info unit). This transaction is the transaction ofinterest. The meta info unit 520 then reads the meta information 401 ofthe transaction and it queries the random access transaction memory 511using various items from the meta information field 401 of thetransaction of interest as parameters. Parameters that may be used arethe IP address of the client or server, or the SSL session ID. Thesetransactions are likely to belong to the web application session of thetransaction of interest.

The random access transaction memory 511 returns to the meta info unit520 a set of transactions that match the search parameters. The metainfo unit 520 places these transactions in the transaction pre-selectionbuffer 521 in chronological order. The set of transactions in thetransaction pre-selection buffer 521 represent the result of a ratherbroad search. This set will be further narrowed in order to isolate thetransactions that belong to the web application session of thetransaction of interest (thus the term “pre-selection”). The transactionpre-selection buffer allows further searches to be performed on thisbroad set of transactions without accessing and slowing down thetransaction storage 204.

The header based transaction correlation unit 522 narrows the set oftransactions in the transaction pre-selection buffer 521, based onrelevant information contained in the request header 402 and responseheader 403 fields of the transaction of interest. Such relevantinformation may include, but is not limited to, cookies, URL-pathcomponents and non-standard headers. This step is meant to discover ifthe web application being monitored is using a session ID that can befound in a transaction's request 402 or response 403 headers, and if soto further narrow down the transactions based on that session ID. Theheader based transaction correlation unit 522 passes the narrowed set oftransactions to the body based transaction correlation and hierarchicallinking unit 523.

The purpose of the body based transaction correlation and hierarchicallinking unit 523 (body based unit) is to determine relationships betweenthe transactions, attempt to find session ID's hidden in the bodies oftransactions, retrieve the bodies of transactions with missing bodies,and reconstruct missing transactions.

The body based unit 523 parses the message bodies 402, 403 of thisnarrowed set of transaction objects. In the embodiments configured tohandle HTTP traffic, an HTML parser is used. However, other parsers maybe used in conjunction with the HTTP traffic if there is a possibilitythat documents in other formats, such as XML, GIF, JPG, Java Script, CSSmay appear. A non-HTML parser may be used if the documents are not inHTML. While being parsed, the HTML bodies of transactions are searchedfor references to other transactions (or web pages consisting of ahierarchy of transactions), or information about the session thetransaction belongs to. References within HTML encoded bodies to othertransactions may include, but are not limited to HTML hyperlinks, HTMLforms, and HTML references to embedded documents. Information about thesession a transaction belongs to may include, but is not limited to,session identifications stored in hidden HTML form fields and sessionidentifications stored in URLs of hyperlinks. These references andsession information are used to discover further relationships betweentransactions and identify transactions as members of the session of thetransaction of interest.

FIG. 7 is a diagram of a data structure that results from parsingseveral transactions that together represent a webpage. The page rootdocument 700 represents the transaction that contains the main HTML codeof a webpage. In this example the data structure further comprises twoframe documents 701, 705, various other embedded documents 702,hyperlinks 703, and web forms 704. Hyperlinks 703 represent HTMLelements within the body of the parent document frame 701. Hyperlinks703 and web-forms 704 refer to root documents of other webpages,contained in other transactions. Embedded documents may be picturefiles, sound files, java programs, etc. All items 700-705 are containedin various transactions within a session. More specifically, all items700-705 are stored in the response bodies 405 of transactions 400. Thereason for this is that in HTTP communications, the client requests adocument, and the server sends that document in a response. If adocument has other documents embedded in it, that document will comprisereferences (usually URLs) of the other documents. Thus, for example,page root document 700 comprises URLs of frames 701, 705.

The body based unit 522 must reconstruct the relationships betweentransactions in webpages (see FIG. 7). For that purpose the body basedunit 522 first finds a transaction that contains a page root document700. Page root documents 700 are identified by the following method.Existing page root documents are checked for references to other pageroot documents. If a document is referenced as a link or a formsubmission of an already identified page root document then it is a pageroot document. If on the other hand a document is referenced as anembedded document in an already identified page root document then it isnot a page root document. If a document is not referenced at all in anyidentified page root documents then it searched for a “text/html”content type header, which would indicate it is a page root document. Ifsuch header is not found, heuristics may be used to determine if it is apage root document. The body based unit then parses each page rootdocument 700. Parsing these page root documents will allow the bodybased unit 522 to find references to other documents in the website thatare embedded directly in the page root document, such as frames 701 and705. Once these references are found the transactions that representthese other documents are found, because they contain these referencesin their request headers. Once these other transactions are found, theyare in turn parsed to find yet more references to embedded documents.This process is repeated recursively until there are no transactionsleft to parse. This process results in hierarchically groupingtransactions into webpages.

After the body based unit 523 has parsed all transactions, it links theparsed transactions in a hierarchical tree 801. This tree is shown inFIG. 8, and will be described with reference to the exemplary embodimentconfigured to monitor HTTP communications. The top level transactions802 in the tree 801 represent the page root documents 700 of suchweb-pages. The other levels of the tree 801 include transactions 803that represent nested documents that are sent by separate messages (ortransactions), such as pictures or other embedded documents, framesetsand frames. Since documents and frames can be embedded in more than onelevel, the tree 801 may have many levels.

Some transaction(s) from the tree 801 may be missing. There is a missingtransaction if a certain first transaction contains a first HTMLdocument which contains an HTML element that indicates that there is asecond document such as an image, HTML frame, or style-sheet embeddedinto the first HTML document, but there is no second transactionconnected to the first transaction that contains the second document.Furthermore, there may exist transactions whose message headers 402 or403 indicate that a certain HTML document is present, but whose messagebodies 405 do not include that document. Both of these possibilitiesresult from the caching features of HTTP communications. Specifically,during a web application session, non-session specific information (suchas static HTML and Image documents) may be cached in the clientcomputer, and then used in a different web application session, withouthaving to be sent from the server to the client for a second time.Furthermore, there may be computers between the client and the server(such as proxies) that perform caching in order to speed upcommunications for the client, and/or reduce bandwidth. Thus, a documentthat is sent to the client during a previous web application sessionwill be placed in a transaction that is identified with the previous webapplication session and thus not included in the set of transactionsexamined by the body based unit 523. Furthermore, there may be HTTPheader fields which reference other documents by specifying an URL (suchas, for example HTTP refresh headers or HTTP redirections). In thesesituations the transaction including the other document is consideredmissing.

The body based unit 523 attempts to retrieve missing transactions, andreplace transactions that do not have message bodies with ones that doby accessing the random access transaction memory 511. For eachtransaction that is missing, or does not contain a message body the bodybased unit 523 queries the random access transaction memory 511 using aURL. The body based unit obtains the needed URL from the parenttransaction of the transaction that is missing or missing a message bodyin the tree 801. The needed URL is the URL referenced by the HTMLelement. The body based unit 523 will thus retrieve most missingdocuments. It will not be able to retrieve any documents that were sentto the client and cached at a time when the RTSRU 112 was notoperational, because no transaction for such documents would have beencreated and saved.

The output of the session reconstruction module 205 and the RTSRU 122 isa hierarchically reconstructed web application session, such as the oneshown in FIG. 8. This session will provide extensive information andcontext about the transaction of interest. And if the transaction ofinterest contained an error message, this session will provide enoughinformation to assist in resolving the error. Similarly, if thetransaction of interest is associated with other issues, such as anexceeded performance threshold, for example, the hierarchicallyreconstructed web application session will be useful in resolving theseissues.

FIG. 9 shows a layered representation of the present invention,including an overview of the data flow. Cable tap 902 or the RMON portof a switch 904, among other options, provide copied network traffic inthe physical layer (layer 1). The standard network module 114 processesthis data to the network layer (layer 3). The stream creation unit 211processes the data to the transport layer (layer 4) by creatingconnection streams. The message decoder processes the data to theapplication layer (layer 7). The session reconstruction module 205 canbe viewed as coherence and organization to the data by placingtransactions in a hierarchically reconstructed session 230. Thehierarchically reconstructed session can be further used by anadditional layer of plug-in applications 900, which provide informationthat is directly useful for a particular testing or monitoring purpose.The plug-in applications listed in FIG. 9 are only some examples ofpossible plug-in applications.

One plug-in application, the script generation module 906, will bedescribed in more detail. A user may wish to repeat the client/servercommunication session that led to the transaction of interest. Doing somay be useful to check whether an error, or another special condition(such as, for example, special keywords, timeouts, usability problems,slow performance) has been resolved, or if an error or another specialcondition is repeatable under different conditions (such as, forexample, different server loads), or to test the performance ofdifferent servers. The hierarchically reconstructed web applicationsession 230 contains a tree of transactions containing a request and aresponse. A script generation tool may use these requests and responsesto create a script, which repeats the requests in the order in whichthey were received by the message decoder 203 and thus recreates the webapplication session, described by the tree 601.

FIG. 10 shows example visual outputs of an exemplary embodiment of thepresent invention. A visualization 1000 of a web application session isshown. Aside from some additional markings, the webpages appear as theywould have appeared to the user. Even webpages that contain frames orother multi-document pages are shown properly due to the structure ofthe hierarchically reconstructed web application session 230. It can beseen that this particular web application session resulted in an error.Also, a generated script 1001 is shown. Both the visualization and thegenerated script were created by plug-in applications, using ahierarchically reconstructed session 230.

The hierarchically reconstructed web application session may be used tomonitor the operation of the server and the client's perspective or itmay be entered into an archive. It may be especially useful to createarchives when certain events take place. The transaction analyzerplug-in 208 may be configured to determine when an event that requiresarchiving takes place and then trigger the retrieval of the webapplication session, by sending the appropriate transaction to thesession reconstruction module 205. Once a hierarchically reconstructedweb application session is retrieved it may be archived. Thus, archivedis not only the transaction that triggered the event but alltransactions leading to the event. The web application sessions may alsogenerate alarms when certain events arise. The hierarchicallyreconstructed web application session may be sent with the alarm inorder to provide contextual information about the session which resultedin an alarm. This and other described functions are performed by one ormore of the plug-in applications 900.

The client/server terminology does not always describe the environmentof a networked computer system accurately. For example, the client andserver roles cannot be specified in a Peer to Peer situation where eachcomputer may act as a client and a server. Nevertheless, theclient/server designations are use both because of their pervasivenessin the field and because they correctly describe most commercialnetworking systems, where the present invention is most likely to beused. The present invention may be used by a person skilled in the artin situations where computers do not necessarily fulfill the client orserver roles exclusively.

The present invention may also be used in networking environments wheremultiple tiers of servers are present. An example of such an environmentis one where a web-server serves clients, the web-server is being servedby an application server, and the application server is being served bya database server. In such an environment the present invention may beused to monitor any or all of the resulting client-server communicationchannels. Furthermore, while the exemplary embodiments have centered onmonitoring of the server, the client may be similarly monitored usingthe present invention.

The exemplary embodiments described herein are centered on monitoringHTTP communications. A person skilled in the art will appreciate thatthe present invention may be used to monitor communications in otherprotocols. The present invention will be especially useful in monitoringcommunications having state information, i.e., communications where inorder to understand the meaning of one transaction, one must look atother transactions.

It is not necessary for the client and server to be computers, thepresent invention may be used for monitoring any electronic devices in anetworked environment.

The standard network module 114 and the RTSRU 112 may be implemented onone or more computers. The present invention may monitor multipleservers and/or as multiple clients. Multiple RTSRU's and standardnetwork modules may be used for scalability purposes. After a slightmodification of the cable-tap setup, the present invention may be usedto monitor multiple communication lines.

While the foregoing description and drawings represent illustrativeembodiments of the present invention, it will be understood that variouschanges and modifications may be made without departing from the spiritand scope of the present invention

SUMMARY OF THE INVENTION

The present invention is directed to a system and method fornon-intrusive monitoring, auditing and testing of a network system, andcompiling information, and generating scripts that may be used fortesting of such a system. The present invention non-intrusively monitorscommunications between two or more machines, reconstructs thisinformation to a higher OSI layer (such as the application layer) inreal-time, decrypts encrypted data and outputs reconstructed monitoringinformation in a hierarchical fashion.

The present invention assists in the monitoring of networking systems bycompiling all the contextual information relating to any event ofinterest. For example, if the event of interest is a website error, thepresent invention outputs the web-page that contained the error, and thesequence of web-pages before this page which might have caused theerror, along with accompanying input information such as text typed bythe end-user into web forms. Thus, the present invention may reconstructall webpages leading to the error in the form in which they appeared tothe user of the client computer. This monitoring information isorganized in a hierarchical fashion according to the relationshipsbetween the different pieces of monitoring information. In this manner,an entire web application session may be reconstructed. The presentinvention provides these monitoring features in real-time.

The ability to obtain contextual information for each event allows thepresent invention to automatically create scripts that function toreproduce a session. A session can be reproduced in order to attempt torepeat an event for debugging or other purposes. Alternatively, asession may be reproduced in order to test whether an error has beenproperly debugged, or to test whether other systems perform in the sameway as the monitored system.

Furthermore, plug-in applications may be used to provide other oradditional features based on the above monitoring features. Plug-inapplications are applications that use gathered monitoring data, inorder to analyze it and/or provide further functionality. Plug-inapplications should be distinguished from server side plug-ins and thetransaction analyzer plug-in. A plug-in application may gatherstatistics of the operation of a server or a client in real time.Examples of useful statistics are, a list of the slowest webpages and alist of the most frequently used search terms. These statistics may beupdated in real-time. Another plug-in application may capture andaggregate the text written by internet users in web forms. This data maylater be used for usability or marketing studies. Another plug-inapplication may assist a customer support professional by showinghim/her in real time all the webpages the customer has seen in aweb-session. Being updated in real time, this information will be quitevaluable for providing informed and efficient customer service.Similarly, a customer service professional may benefit from observing aperson's web session in real time in order to provide informed phonesupport.

Another plug-in application may gather performance monitoringinformation. This may be accomplished in real-time and in anon-intrusive manner. In addition, the present invention allows both theserver's and the client's performance information to be gathered. Thisprovides the ability to determine whether a reported performance problemwas caused by the server or the client. The present invention allows forgathering genuine performance monitoring information, i.e., theperformance monitoring information is gathered in the course of ordinarybusiness from real clients, in lieu of or in addition to the use ofsimulation or testing clients. Performance monitoring information may becombined with or embedded in reconstructed web sessions.

A plug-in application may also be used to monitor abandonment rates.Session abandonment occurs when a person leaves a website before thatperson completes a desired task. The desired task may be a purchase, asign up, a download, or any other task. The present invention mayfurther match each abandoned session with the performance monitoringinformation of that session and thus provide data that will be useful indetermining the direct influence of performance on client conduct.Transaction abandonment occurs when a person discontinues acommunication while waiting for a response form a remote computer. Forexample, a person may navigate an internet browser to a website whichresults in a request for a webpage from a server. If the person pressesthe stop button of his/her browser (or directs the browser to adifferent webpage) before the webpage has been received, transactionabandonment has occurred. Transaction abandonment can occur with orwithout session abandonment. Transaction abandonment information mayalso be combined with performance monitoring information.

Another plug-in application may detect anomalies at the transport layer(OSI layer 4) of communication, such as, abnormal number of TCPreconnects, connection timeouts, packet resends, etc. These anomaliesmay be a sign of a malfunctioning or improperly configured network.

Although the HTTP and HTTPS protocols are used as examples in describingthe present invention, the present invention may be used to monitorapplications communicating using other protocols, such as SOAP, POP3,SMTP, FTP, IMAP4, RMI, WSP/WTP. The present invention may use the TCPtransport protocol as well as other transport protocols such as UDP andWDP.

1. A method for non-intrusive real-time analysis of securecommunications between a first application and a second application,wherein the first and second applications communicate through acommunication channel, comprising the steps of: non-intrusively andsecurely capturing a plurality of secure communications between thefirst application and the second application substantially in real-time;processing the plurality of communications to form a first plurality ofinformation units, each information unit comprising application levelinformation substantially in real-time; analyzing a second plurality ofinformation units up to an application layer, the second pluralitycomprising one or more of the first plurality of information units, todetermine a plurality of dependencies among the second plurality ofinformation units substantially in real-time; organizing the secondplurality of information units into a hierarchical data structureaccording to the plurality of dependencies among the information units.